This repository has been archived by the owner on May 23, 2023. It is now read-only.
Initial implementation of a no-op active Span. #320
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey all,
I decided to test out, as a prototype, a no-op active
Scope
/Span
for the current api. This had been suggested (or at least mentioned) in the past. And it could probably help with features such as #319Advantages:
ScopeManager.active()
norScopeManager.activeSpan()
.Potential issues:
MockTracer
which will check againstNoopSpanContext
, and which case it will ignore it as potential parent when creating newSpan
s.assertEquals(NoopScope.INSTANCE, scopeManager.active())
instead ofassertNull(scopeManager.active())
.Thoughts?
@yurishkuro @felixbarny @tedsuo @sjoerdtalsma @tylerbenson @opentracing/opentracing-java-maintainers
PS - Did not update the testbed module. Will do that later if we decide to go on and merge this change ;)